fix: escape inline subscripts on real Grothendieck constant page#104
Open
Chessing234 wants to merge 1 commit into
Open
fix: escape inline subscripts on real Grothendieck constant page#104Chessing234 wants to merge 1 commit into
Chessing234 wants to merge 1 commit into
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
_in the$C_{10}$/$K_G$definition onconstants/10a.md.Root cause
Kramdown treats consecutive underscores as emphasis (#8). PR #11 fixed this on the old
constants/10.md; the split into10a.mddropped the escaping, so the Grothendieck constant definition renders incorrectly on the site.Fix
Use
\_in inline math, matching #96–#100.Test plan
$C_{10}$and$K_G$correctlyMade with Cursor